cacls /some/directory/jmxremote.password /P username:R
|
Internal Name: |
JMX Server |
|
Description: |
Generic JMX Server |
|
Singleton: |
no |
|
Plugin: |
JMX |
In order to monitor your Java applications via JMX, you need to expose their MBeans to remote JMX clients.
In order to do this, you must pass in some system properties when starting your application's Java virtual
machine.
To run a JVM with JMX remoting enabled without authentication, you must pass in the following system
properties:
-Dcom.sun.management.jmxremote.port=19988
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
You can require your remote JMX endpoint to demand authentication for clients to be able to connect to it.
To run a JVM with JMX remoting enabled with password authentication:
-Dcom.sun.management.jmxremote.port=19988
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=/some/directory/jmxremote.password
Note that "jmxremote.password" must be read-only. On Windows, you must use "cacls" command to do this:
cacls /some/directory/jmxremote.password /P username:R
A password file template is located at $JRE_HOME/lib/management/jmxremote.password.template. There is also
an auth file that you can use to define other roles. For more information on setting this up and setting up
SSL, see Monitoring and Management Using JMX.
If you wish to expose your JBossAS 4 application server's MBeans over this remote JMX mechanism, you must
pass in these extra properties, in addition to the properties specified above:
-Djboss.platform.mbeanserver
-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
|
Name |
Query |
|
java |
process|basename|match=^java.* |
|
Name |
Description |
Required |
Internal Name |
|
Type |
The EMS connection type for this JMX Server |
yes |
type |
|
Connector Address |
The connection url in the form of a JMXServiceURL - this should only be set if the JVM has JMX Remoting enabled |
no |
connectorAddress |
|
Install URI |
The installation path for the selected server type which will be used to find client libraries (if appropriate) |
no |
installURI |
|
Principal |
The login principal/username |
no |
principal |
|
Credentials |
The login credentials/password |
no |
credentials |
|
Additional Class Path Entries |
Comma-separated list of directories and filenames that contain resources and classes needed to communicate with the JMX Server and its MBeans. If you specify 'some/directory/*.jar', all jars found in the given directory will be added. |
no |
additionalClassPathEntries |
|
Command Line |
the command line of the JVM at the time it was discovered - only used by JVMs with type Local; if the command line of the JVM changes, this property's value will need to be updated accordingly in order for RHQ to connect to the JVM |
no |
commandLine |
You must use the internal name to reference properties in Dynamic Group Definition expressions.